<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
<HEAD>

<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<TITLE>
Preference pages
</TITLE>

<link rel="stylesheet" type="text/css" HREF="../book.css">
</HEAD>
<BODY BGCOLOR="#ffffff">
<h2>
Preference pages</h2>
<p>
Once a plug-in has contributed extensions to the workbench user interface, it is common for
the plug-in to allow the user to control some of the behavior of the plug-in through
user preferences.
</p>
<p>
The platform UI provides support for storing plug-in preferences and showing them to the user
on pages in the workbench <b>Preferences</b> dialog. Plug-in preferences are key/value pairs, where the 
key describes the name of the preference, and the value is one of several different types.  (See
<a href="runtime_preferences.htm">Runtime preferences</a> for a detailed description of 
the runtime preferences infrastructure.)</p>
<p>How does a plug-in contribute a page for showing its preferences?  We will use the readme 
tool example to see how it contributes a preference page to the
workbench and then look at some of the underlying support for building preference pages.</p>



</BODY>
</HTML>
